Check if this issue is valid — if so, understand the root cause and fix it. At examples/06-multi-repo-migration/taskspawners.yaml, line 25:

<comment>`# TODO: replace with actual migration` is inside a YAML block scalar (`|`), so it will be sent as literal text to the AI agent — it is NOT a YAML comment. This is inconsistent with the other `# TODO:` placeholders in this file (e.g., on `schedule:` lines) which are real YAML comments. Move this TODO to a YAML comment above the `promptTemplate:` key so users see it but the agent doesn't.</comment>

<file context>
@@ -0,0 +1,106 @@
+      Migrate this repository from the deprecated `log/v1` package to `log/v2`.
+
+      Steps:
+      1. Find all imports of `github.com/your-org/log/v1`. # TODO: replace with actual migration
+      2. Replace them with `github.com/your-org/log/v2`.
+      3. Update any changed API calls (see migration guide below).
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At examples/05-pr-review-spawner/agentconfig.yaml, line 30:

<comment>Using `--body "<review>"` is fragile — code reviews routinely contain double quotes, backticks, and other shell metacharacters that will break this command. Prefer `--body-file` to avoid shell quoting issues.</comment>

<file context>
@@ -0,0 +1,31 @@
+            2. Read the diff: `git diff main...HEAD`
+            3. Read the PR description: `gh pr view <number>`
+            4. Read any existing review comments: `gh api repos/{owner}/{repo}/pulls/<number>/comments`
+            5. Post your review: `gh pr review <number> --comment --body "<review>"`
+            6. Swap the labels: `gh pr edit <number> --remove-label needs-ai-review --add-label ai-reviewed`
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At examples/06-multi-repo-migration/README.md, line 43:

<comment>Inconsistent CLI usage: this example uses `axon get tasks -w` but examples 01–04 and the parent `examples/README.md` all use `kubectl get tasks -w`. Use `kubectl` for consistency, or update all examples together.</comment>

<file context>
@@ -0,0 +1,53 @@
+4. Monitor progress:
+
+```bash
+axon get tasks -w
+```
+
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At examples/06-multi-repo-migration/README.md, line 9:

<comment>The "How It Works" section opens with "A single TaskSpawner" which contradicts the actual pattern (one TaskSpawner per repo) clarified two paragraphs later. This will confuse readers. Consider rewriting the opening to accurately describe the architecture from the start.</comment>

<file context>
@@ -0,0 +1,53 @@
+
+## How It Works
+
+Each repository gets its own Workspace resource. A single TaskSpawner on
+a cron schedule creates one Task per Workspace. Axon handles the
+parallelism — all agents run concurrently in isolated Pods.
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At examples/07-security-audit-cron/taskspawner.yaml, line 28:

<comment>Incorrect command name: `go vuln check` doesn't exist. The Go vulnerability scanning tool is `govulncheck` (single word, separate tool). An AI agent following this prompt would fail to run the vulnerability scan.</comment>

<file context>
@@ -0,0 +1,41 @@
+         passwords in source files — not test fixtures or examples).
+      2. Review dependency files (go.mod, package.json, requirements.txt, etc.)
+         for known vulnerabilities. Use available tools if present (e.g.,
+         `go vuln check`, `npm audit`).
+      3. Scan for injection vulnerabilities in code that handles user input.
+      4. Check configuration files for insecure defaults.
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At examples/07-security-audit-cron/README.md, line 38:

<comment>Inconsistent CLI usage: this example uses `axon` commands while existing examples and the main `examples/README.md` use `kubectl`. The main README lists only `kubectl` as a prerequisite; users may not have the `axon` CLI installed. Consider using `kubectl` for consistency, or update the main README to list `axon` as a prerequisite.</comment>

<file context>
@@ -0,0 +1,47 @@
+3. Check results after the next cron tick:
+
+```bash
+axon get tasks
+axon logs <task-name>
+```
</file context>